Analytics-driven dynamic network design and configuration

ABSTRACT

A system and method for dynamically (re)configuring a service network based on profile information obtained from a Big Data Analytics platform. Received dynamic situation profiles relative to network states, subscriber states, etc. may be compared against corresponding characteristic situation profiles. If there is a similarity, a dynamic design change action may be effectuated for changing configuration of at least a part of the service network, e.g., a service chaining mechanism, operating to service user data flows of the subscribers.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to the field of networks. Moreparticularly, and not by way of any limitation, the present disclosureis directed to analytics-driven dynamic network design andconfiguration, e.g., with respect to one or more services in a network.

BACKGROUND

Operators use different middlebox services or appliances, called inlineservices, such as Deep Packet Inspection (DPI),logging/metering/charging/advanced charging, Firewall, IntrusionDetection and Prevention (IDP), Network Address Translation (NAT), etc.,to manage subscribers' traffic. These services have high requirements onthroughput and packet inspection capabilities. They can be transparentor nontransparent to the end users. Services can be hosted on dedicatedphysical hardware or in virtual machines.

Service chaining may be required if the traffic needs to go through morethan one inline service or service function. Moreover, if more than onechain of services is possible, the operator needs to configure thenetworking infrastructure efficiently so as to direct the right trafficvia the right inline service path depending on service policies andrequirements.

SUMMARY

The present patent disclosure is broadly directed to a scheme forproviding analytics-driven dynamic network design and configuration withrespect to a network, e.g., including one or more service functions(SFs) or virtual network functions (VNFs) in a service network. In oneaspect, an embodiment of a method for network configuration comprises,inter alia, receiving, from a data analytics platform, a dynamicsituation profile with respect to a particular situation defined interms of one or more service user behavior events and/or one or moreevents pertaining to a state of a network servicing a plurality ofservice users. The dynamic situation profile preferably comprises valuesor measurements or other indicia corresponding to the service userbehavior events and/or the network state events defining the particularsituation, as monitored and gathered by the data analytics platform,which may be implemented as a Big Data Analytics platform. A similarityindex between the dynamic situation profile and a characteristicsituation profile corresponding to the particular situation may bedetermined (e.g., within a configurable tolerance or window), whereinthe characteristic situation profile comprises allowable values (e.g.,threshold values) with respect to the service user behavior eventsand/or the network state events defining the particular situation. Ifthe similarity index is within an acceptable window, one or more controlsignals may be generated to effectuate a dynamic design change actionfor changing configuration of at least a part of the network operatingto service data flows of the service users (e.g., a service chainmechanism provided in virtualized infrastructure).

In another aspect, an embodiment of a network element operative with aservice network is disclosed. The claimed embodiment comprises, interalia, a profile analyzer operative to receive from a data analyticsplatform a dynamic situation profile with respect to a particularsituation defined in terms of one or more service user behavior eventsand/or one or more events pertaining to a state of a network servicing aplurality of service users. As set forth above, the dynamic situationprofile preferably comprises values or measurements or other indiciacorresponding to the service user behavior events and/or the networkstate events defining the particular situation, as monitored andgathered by the data analytics platform, which may be implemented as aBig Data Analytics platform. A matching module associated with theprofile analyzer is configured to determine a similarity index betweenthe dynamic situation profile and a characteristic situation profilecorresponding to the particular situation, wherein the characteristicsituation profile comprises allowable (e.g., threshold) values withrespect to the service user behavior events and/or the network stateevents defining the particular situation. A dynamic service chaindesigner is operative responsive to receiving an indication that thesimilarity index between the dynamic situation profile and thecharacteristic situation profile is within an acceptable window, forgenerating one or more control signals to effectuate a dynamic designchange action for changing configuration of at least a part of thenetwork operating to service user data flows of the service users (e.g.,a service chain mechanism provided in virtualized infrastructure).

In a still further aspect, an embodiment of a non-transitorycomputer-readable medium containing instructions stored thereon isdisclosed for performing one or more embodiments of the methods setforth herein. In one variation, an embodiment of a configurable networkcomprises a service network that is architected as a Software DefinedNetwork (SDN). In another variation, the service network may embodynon-SDN architectures. In still further variations, the service networkcomprises a network having service functions that may be at leastpartially virtualized. It will therefore be realized that the teachingshereof may be practiced in any network having a combination of theforegoing features. Furthermore, it should be appreciated that theforegoing methods, systems, apparatuses and/or computer-readable mediamay be implemented within a variety of networks and/or network domains,e.g., as additional or alternative embodiments adapted for dynamicdesign and configuration of private, public and corporate networks, anddata centers, personal networks, data communication networks,telecommunication networks, content delivery networks, enterprisenetworks, intranets, and the like. Since an embodiment of the presentinvention involving data analytics-driven network design andconfiguration may be used in any domain, whether service functionsvirtualized or not, example implementations may include but not limitedto domains such as a telecom domain having wireless LTE service nodes(e.g., MME, PGW, SGW, etc.) as well as financial network domains havingfinancial service nodes and healthcare domains having healthcare servicenodes. It should therefore be appreciated that the term “servicenetwork”, for purposes of the present patent application, may includeany of the foregoing types of networks and/or domains, depending on thecontext and specific implementation.

Benefits of the present invention include, but not limited to, providingan embodiment that advantageously leverages Big Data Analytics todynamically derive suitable rules for the instantiation, maintenance ortermination of service functions based on real-time data gathering,monitoring and analysis. Because of the use of more up-to-date data,faster convergence to optimized placement and/or assignment ofmulti-instances of service functions may be achieved, either in reactivemode, proactive mode, or both, with respect to a service network havingone or more service chaining policies. Moreover, as default assignmentscan be changed dynamically, service network operators can bring moreservices online without significantly impacting scalability. Furtherfeatures of the various embodiments are as claimed in the dependentclaims. Additional benefits and advantages of the embodiments will beapparent in view of the following description and accompanying Figures.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present disclosure are illustrated by way of example,and not by way of limitation, in the Figures of the accompanyingdrawings in which like references indicate similar elements. It shouldbe noted that different references to “an” or “one” embodiment in thisdisclosure are not necessarily to the same embodiment, and suchreferences may mean at least one. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to effect such feature, structure, or characteristicin connection with other embodiments whether or not explicitlydescribed.

The accompanying drawings are incorporated into and form a part of thespecification to illustrate one or more exemplary embodiments of thepresent disclosure. Various advantages and features of the disclosurewill be understood from the following Detailed Description taken inconnection with the appended claims and with reference to the attacheddrawing Figures in which:

FIG. 1 depicts an example network architecture wherein one or moreembodiments of the present patent application may be practiced forconfiguring or reconfiguring a network based on dynamic profileinformation obtained from a data analytics platform;

FIG. 2 depicts an example service network that may be configured orreconfigured for effectuating dynamic service chain design according toan embodiment;

FIG. 3 depicts a network function virtualization (NFV) architecture thatmay be applied to the example service network of FIG. 2;

FIG. 4 depicts an analytics-driven network architecture for dynamicallyconfiguring or reconfiguring services and/or service chaining in anNFV-based service network of FIG. 2;

FIG. 5 depicts a block diagram of a network element or subsystem thatincludes various components for effectuating a network (re)configurationscheme according to an embodiment;

FIG. 6 depicts a flowchart of various blocks, steps, acts and functionsthat may take place in a network (re)configuration scheme according toan embodiment;

FIG. 7 depicts a flowchart of various blocks, steps, acts and functionsthat may take place in a network (re)configuration scheme according toanother embodiment; and

FIG. 8 depicts a block diagram of a network element or subsystem thatmay be configured to interoperate in an analytics-driven networkarchitecture according to an embodiment of the present patentdisclosure.

DETAILED DESCRIPTION OF THE DRAWINGS

In the following description, numerous specific details are set forthwith respect to one or more embodiments of the present patentdisclosure. However, it should be understood that one or moreembodiments may be practiced without such specific details. In otherinstances, well-known circuits, subsystems, components, structures andtechniques have not been shown in detail in order not to obscure theunderstanding of the example embodiments. Accordingly, it will beappreciated by one skilled in the art that one or more embodiments ofthe present disclosure may be practiced without such specificcomponents-based details. It should be further recognized that those ofordinary skill in the art, with the aid of the Detailed Description setforth herein and taking reference to the accompanying drawings, will beable to make and use one or more embodiments without undueexperimentation.

Additionally, terms such as “coupled” and “connected,” along with theirderivatives, may be used in the following description, claims, or both.It should be understood that these terms are not necessarily intended assynonyms for each other. “Coupled” may be used to indicate that two ormore elements, which may or may not be in direct physical or electricalcontact with each other, co-operate or interact with each other.“Connected” may be used to indicate the establishment of communication,i.e., a communicative relationship, between two or more elements thatare coupled with each other. Further, in one or more example embodimentsset forth herein, generally speaking, an element, component or modulemay be configured to perform a function if the element is capable ofperforming or otherwise structurally arranged to perform that function.

As used herein, a network element or node (e.g., a router, switch,bridge, etc.) is a piece of networking equipment, including hardware andsoftware that communicatively interconnects other equipment on a network(e.g., other network elements, end stations, etc.). Some networkelements may comprise “multiple services network elements” that providesupport for multiple networking functions (e.g., routing, bridging,switching, Layer-2 aggregation, session border control, Quality ofService, and/or subscriber management, and the like), and/or providesupport for multiple application services (e.g., data, voice, andvideo). In some implementations, a network element may also include anetwork management element and/or vice versa. Subscriber end stations(e.g., servers, workstations, laptops, notebooks, palm tops, mobilephones, smartphones, multimedia phones, Voice Over Internet Protocol(VOIP) phones, user equipment, terminals, portable media players, GPSunits, gaming systems, set-top boxes) may access or consumecontent/services provided over a packet-switched wide area publicnetwork such as the Internet via suitable service provider accessnetworks. Subscriber end stations may also access or consumecontent/services provided on virtual private networks (VPNs) overlaid on(e.g., tunneled through) the Internet. Whereas some network nodes orelements may be disposed in wired communication networks, others may bedisposed in wireless infrastructures. Further, it should be appreciatedthat example network nodes may be deployed at various hierarchicallevels of an end-to-end network architecture. Regardless of the specificimplementation, one skilled in the art will recognize that one or moreembodiments of the present patent disclosure may involve a configurablenetwork or a portion thereof, e.g., such as a service network having aplurality of network nodes (i.e., switches or elements interconnected ina topological arrangement) wherein one or more services or servicefunctions having multiple instances (i.e., “service function replicas”)may be placed for traversal by a plurality of subscriber data flows(generated by or involving any type of above-described subscriber endstations) according to known or otherwise preconfigured servicerequirements and/or dynamically (re)configurable service rules andpolicies. Additionally, one or more embodiments of the presentdisclosure may be practiced in a service network that may be implementedin a Software Defined Network (SDN) architecture, which may furtherinvolve varying levels of virtualization, e.g., virtual appliances forsupporting virtualized service functions or instances a suitable networkfunction virtualization (NFV) infrastructure.

One or more embodiments of the present patent disclosure may beimplemented using different combinations of software, firmware, and/orhardware. Thus, one or more of the techniques shown in the Figures(e.g., flowcharts) may be implemented using code and data stored andexecuted on one or more electronic devices (e.g., an end station, anetwork element, etc.). Such electronic devices may store andcommunicate (internally and/or with other electronic devices over anetwork) code and data using computer-readable media, such asnon-transitory computer-readable storage media (e.g., magnetic disks,optical disks, random access memory, read-only memory, flash memorydevices, phase-change memory, etc.), transitory computer-readabletransmission media (e.g., electrical, optical, acoustical or other formof propagated signals—such as carrier waves, infrared signals, digitalsignals), etc. In addition, such electronic devices may typicallyinclude a set of one or more processors coupled to one or more othercomponents, such as one or more storage devices (non-transitorymachine-readable storage media), user input/output devices (e.g., akeyboard, a touch screen, a pointing device, and/or a display), andnetwork connections. The coupling of the set of processors and othercomponents may be typically through one or more buses and bridges (alsotermed as bus controllers), arranged in any known (e.g.,symmetric/shared multiprocessing) or heretofore unknown architectures.Thus, the storage device or component of a given electronic device maybe configured to store code and/or data for execution on one or moreprocessors of that electronic device for purposes of implementing one ormore techniques of the present disclosure.

Turning now to FIG. 1, depicted therein is an example networkarchitecture 100 wherein one or more embodiments of the presentinvention may be practiced for configuring or reconfiguring a network108 based on dynamic profile information obtained from a data analyticsplatform 104. For purposes of the present patent disclosure, the terms“configure” and “reconfigure” will be used somewhat interchangeablydepending on the context wherein one term may include the other. Inaccordance with the teachings herein, a data analytics service platform104 is operative to receive, monitor, obtain, measure, or otherwisedetermine various pieces of data or information via one or more suitablecommunication network paths 110 (which may involve networkinfrastructure including, e.g., a public network such as the Internet, aprivate network, an enterprise network, a corporate network, or anycombination thereof), at least part of which data or information may berelevant with respect to one or more environmental states of theconfigurable network 108. By way of illustration, example environmentalstates of the network 108 may comprise one or more states or conditionsrelating to the network infrastructure, e.g., underlying physical and/orvirtual resources, network traffic conditions, etc., as well as thestates and conditions relating to the service users or subscribersserved by the network 108, including the service user behavior statesand user data flows therein. Accordingly, data 106 regarding userstates, network states and any internal/external events orconditionalities having a relationship or impact thereon, may begathered, obtained or monitored by the data analytics platform 104. Inone example implementation, the data analytics service platform 104 maybe configured as a “Big Data” analytics platform for advantageouslyanalyzing vast amounts of information that may be processed to providesuitable sets of multidimensional data, which may be referred to hereinas “profiles”, to a network node or subsystem 102. Preferably, thenetwork node or subsystem 102 may be configured to generate one or morecontrols signals for effectuating suitable dynamic design change actionswith respect to (re)configuring the network 108 under a knowledge-based,user-trainable profile analysis and network designer mechanism as setforth in further detail below. Furthermore, in some exampleimplementations, the network node or subsystem 102 may be adapted tointeroperate with an Operation Support System (OSS) or, more generally,an orchestrator, of the network domain. In a still further embodiment,one or more aspects of the network node 102 may be integrated within anorchestrator of the network domain.

For purposes of the present application, “Big Data” may be used as aterm for a collection of data sets so large and complex that it becomesvirtually impossible to process using conventional database managementtools or traditional data processing applications in a scalable manner.Challenges involving Big Data may include capture, curation, storage,search, sharing, transfer, analysis, and visualization, etc. Because BigData available with respect to user states, network states, and otherrelevant variables (e.g., real-time data relating to the type(s) offlows, content types, content availability and scheduling, networkcongestion, as well as geographic and other location-based information,etc.) can be on the order of several terabytes to petabytes to exabytesdepending on the number of subscribers, complexity of the network,geographic area(s) covered by the network, and the like, it becomesexceedingly difficult to work with using most relational databasemanagement systems for optimizing, ranking, correlating and indexingenvironmental state data in typical environments. In one embodiment, theanalytics service platform 104 may be implemented as a programming modelframework for processing and analyzing large data sets with a parallel,distributed algorithmic engine that may be executed in a “massivelyparallel processing” (MPP) architecture with software running on a largenumber of servers (e.g., a server farm). For example, a MapReduceprogramming platform may be configured as an implementation of theanalytics service platform 104 for analyzing the gathered informationand correlating to the subscriber activity and network states.Accordingly, in one example configuration, the data analytics platform104 may be implemented in an open-source software framework such as,e.g., Apache Hadoop, that is optimized for storage and large-scaleprocessing of data sets on clusters of commodity hardware. In addition,the data analytics platform 104 may also employ suitable machinelearning (ML) techniques, support vector machines (SVMs) or supportvector networks (SVNs), pattern recognition, artificial intelligence(AI) techniques, neural networks, and the like, for adaptivelypredicting/learning what variables/information to monitor with respectto the changing environmental states of the configurable network 108. Itshould be appreciated that although FIG. 1 shows the data analyticsservice platform 104 as a separate or single entity, such a platform maybe disposed at different locations in the network, or distributed acrossmultiple networks or elements, or otherwise at least partiallyco-located or integrated within an operator network.

FIG. 2 depicts an example service network 200 that may be operative asthe configurable network 108 of FIG. 1 in an illustrative embodiment. Aplurality of ingress nodes 206-1 to 206-M and a plurality of egressnodes 208-1 to 208-K bound the service network 200, wherein anembodiment of the present patent disclosure may be practiced forpurposes of dynamically configuring and/or reconfiguring one or moreservice chains involving various service functions within the network.Reference numerals 210-1 to 210-L refer to a plurality of dataforwarding nodes coupled together in a topological configuration foreffectuating routing of incoming data packet flows 202-1 to 202-Nreceived from source domains at the ingress nodes 206-1 to 206-M to theegress nodes 208-1 to 208-K that emit outgoing data packet flows 204-1to 204-N to external domains. It should be appreciated that the routingof data packets within the network 200 may be effectuated using anyknown class of routing protocols between any two nodes in the network,such as, e.g., a link-state routing protocol or a distance-vectorrouting protocol. Reference numerals 212-1 to 212-I refer to one or moreinline services that are to be placed or configured within the network200 which the incoming subscriber data flows 202-1 to 202-N may berequired to traverse in a sequential order based on subscriber and/oroperator policies, service chaining requirements, and the like. By wayof example, such services may comprise Deep Packet Inspection (DPI),Virus Scanning (VS), Intrusion Detection and Prevention (IDP), Firewall(FW) filtering, Network Address Translation (NAT), and the like.Further, one or more of such inline services may be provided in multipleinstances or replicas, which may be deployed by the network operator forload-balancing, for example.

By way of illustration, the example service network 200 may bearchitected as a Software-Defined Network (SDN) based on known protocolssuch as, e.g., OpenFlow (OF) protocol, Forwarding and Control ElementSeparation (ForCES) protocol, etc., although it should be appreciatedthat the embodiments described herein may be practiced in conjunctionwith other network architectures, including non-SDN architectures, aswell. An example SDN architecture typically involves separation anddecoupling of the control and data planes of the network elements,whereby network intelligence and state control may be logicallycentralized and the underlying network infrastructure is abstracted fromthe applications. One implementation of an SDN-based service network maytherefore comprise a network-wide control platform, executing on or moreservers in the network, which is configured to oversee and control aplurality of data forwarding nodes or switches. Accordingly, astandardized interfacing may be provided between the network-widecontrol platform (which may be referred to as a “central controller” forpurposes of some embodiments of the present patent application) and thedata switching/forwarding nodes, thereby facilitating high scalability,flow-based services chaining, multi-tenancy and secure infrastructuresharing, virtual overlay networking, efficient load balancing, and thelike. In contrast, other embodiments may follow an integrated designwhere the control plane and data-forwarding plane are tightly coupled inthe same network element, which usually results in a more complicatedcontrol plane and complex network management, with concomitantshortcomings and deficiencies such as diminished scalability,adaptability and resource optimization.

A typical SDN switching node comprises a flow table, which performspacket lookup and forwarding, and a secure channel that connects one ormore switches to the central controller, allowing commands and packetsto be sent therebetween using an open and standard protocol. The maintask of a forwarding element, or a switch, is to forward packets from aningress port to an egress port, according to the rules in the flow tableprogrammed by the controller. The flow table may contain a set of flowentries, activity counters, and a set of one or more actions to apply tomatching packets. For instance, a flow entry may be configured with aset of actions such as: forwarding packets to a given port, modifyingcertain bits in the packet header, encapsulating packets to thecontroller, or simply dropping the packets. For the first packet in anew flow, the switch normally forwards the packet to the controller totrigger the new flow entry being programmed. In certain embodiments, aswitch can also be used to forward all slow-path packets, e.g., InternetControl Message Protocol (ICMP) packets, to the controller forprocessing. It should be appreciated that the concept of a data packetflow can be defined broadly, e.g., a Transmission Control Protocol (TCP)connection, or all traffic from a particular Media Access Control (MAC)address or Internet Protocol (IP) address, or all packets with the sameVirtual LAN (VLAN) tag, or all packets from the same switch port, or alltraffic having one or more user-defined control flags, as well asincluding any combination of the foregoing conditionalities.

With respect to the example network implementation illustrated in FIG.2, a network-wide controller 215 may be provided for implementing thecontrol plane operations of the network 200 using a standardizedinterfacing architecture relative to the remaining network components,as exemplified by interfaces 216, 218. The network controller 215 may beoperative to add and remove flow-entries from the flow tables, e.g., aspart of defining the interconnection and routing among the set of dataplane switches 210. The network controller 215 also handles networkstate distribution, such as collecting information from, anddistributing routing instructions to, the switches. The networkcontroller 215 can also be programmed to support any new addressing,routing, and complex packet processing applications. Accordingly, thenetwork controller 215 may be deemed the “brain” of the example servicenetwork 200 (which may also be referred to as a service provider networkin certain implementations), wherein a switch may be required to connectto at least one controller functionality in order to operate properly.

It should be appreciated that the ingress and egress nodes of theexample network 200 of FIG. 2 are placed at the perimeter of the network200, wherein the ingress nodes 206-1 to 206-M may be configured toclassify an incoming traffic flow and steer it towards the next servicebased on one or more services chaining (SC) policies, rules and otherservice requirements (collectively illustrated as service requirementsdatabase 214) using a traffic steering mechanism executed by thecontroller node 215. Additional details regarding an example trafficsteering implementation and placement of services in an SDN architecturemay be found in one or more of the following commonly owned U.S. patentapplication(s) and/or issued patents: (i) “SERVICE PLACEMENT FOR INLINESERVICE CHAINING WITH MULTIPLE INSTANCES”, application Ser. No.14/026,344, filed Sep. 13, 2013, issued as U.S. Pat. No. 8,817,625; (ii)“CHAINING OF INLINES SERVICES USING SOFTWARE DEFINED NETWORKING”,application Ser. No. 13/556,456, filed Jul. 24, 2012, published as U.S.Patent App. Publication No.: 2013/0272305; and (ii) “METHOD ANDAPPARATUS FOR PLACING SERVICES IN A NETWORK”, application Ser. No.13/751,826, filed Jan. 28, 2013, published as U.S. Patent App.Publication No.: 2014/0215074, hereby incorporated by reference herein.

FIG. 3 depicts a network function virtualization (NFV) architecture 300that may be applied to the example service network 200 of FIG. 2.Various physical resources and services executing thereon within thenetwork 200 may be provided as virtual appliances wherein the resourcesand service functions are virtualized into suitable virtual networkfunctions (VNFs) via a virtualization layer 310. Resources 302comprising compute resources 304, memory resources 306, and networkinfrastructure resources 308 are virtualized into corresponding virtualresources 312 wherein virtual compute resources 314, virtual memoryresources 316 and virtual network resources 318 are collectivelyoperative to support a VNF layer 320 including a plurality of VNFs 322-1to 322-N. Virtualization layer 310 (also sometimes referred to asvirtual machine monitor (VMM) or “hypervisor”) together with thephysical resources 302 and virtual resources 312 may be referred to asNFV infrastructure (NFVI) of a network environment. Overall NFVmanagement and orchestration functionality 326 may be supported by avirtualized infrastructure manager (VIM) 332, a VNF manager 330 and anorchestrator 328, wherein VIM 332 and VNF manager 330 are interfacedwith NFVI layer and VNF layer, respectively. An Operation Support System(OSS) and/or Business Support System (BSS) component or element 324 isresponsible for network-level functionalities such as networkmanagement, fault management, configuration management, servicemanagement, and subscriber management, etc., which may interface withVNF layer 320 and NFV orchestration 328 via suitable interfaces. Inaddition, OSS/BSS 324 may be interfaced with a configuration module 334for facilitating service, VNF and infrastructure description input.Broadly, NFV orchestration 328 involves generating, maintaining andtearing down of network services or service functions supported bycorresponding VNFs, including creating end-to-end services over multipleVNFs in the service network (i.e., service chaining for various dataflows from ingress nodes to egress nodes). Further, NFV orchestrator 328is also responsible for global resource management of NFVI resources,e.g., managing compute, storage and networking resources among multipleVIMs in the network.

Based on the foregoing, it should be appreciated that in the context ofthe present application, a service function (SF) (also sometimesreferred to as a network function or NF) is a function that isresponsible for specific treatment of received packets of a subscriberdata flow. A service function can act at various layers of a protocolstack (e.g., at the network layer or other OSI layers). Furthermore, asa logical component, a service function can be realized as a virtualelement or be embedded in a physical network element. In someimplementations, one or more service functions can be embedded in thesame network element. Also, multiple occurrences or instances of aservice function (referred to as replicas hereinabove) can exist in thesame administrative domain. Because the physical resources allocated toa VNF are considered to be elastic and the VNFs can run on multiplephysical infrastructure network nodes, there is a loose coupling betweenthe VNFs and the physical infrastructure hardware nodes they exist on,which allows greater scalability and dynamic configurability of avirtualized network environment. Although the teachings of the presentapplication are particularly set forth with respect to a virtualizedservice network wherein an arrangement of virtual SFs (or synonymously,VNFs) may be dynamically (re)configured according to an embodiment, oneskilled in the art will recognize that such teachings are alsoapplicable to other network embodiments having embedded functionalities,e.g., embedded SFs, mutatis mutandis. In similar fashion, not allembodiments of the present invention may involve an SDN-based servicenetwork.

A service function chain or virtual network function (VNF) chain (whichmay be commonly referred to herein as an “SC” for short) within anexample service network defines an ordered or partially ordered set ofabstract service functions and ordering constraints, rules or policiesthat must be applied to packets so as to steer packet flows through theSF/VNFs that comprise an end-to-end service instantiated by the servicechain. As described above with respect to FIG. 2, an atomic example ofan abstract service function is a Firewall. Additional examples of VNFsinclude, but are not limited to, Intrusion Detection and PreventionSystems (IDS/IPS), content filters and optimization mechanisms, DPI,NAT, caching, Lawful Intercept (LI), server load balancing, contentdistribution nodes (CDNs), etc., at least some which have beenreferenced hereinabove with respect to the SDN arrangement of FIG. 2.Still further examples in carrier networks include Mobile Core and IMSservers (Mobile Management Entities (MMEs), Packet Data Network Gateways(PGWs), Servicing Gateways (SGWs) and Call Session Control Functions(CSCFs) and Fixed Network servers, such as Digital Subscriber LineAccess Multiplexers (DSLAMs).

Typically, the implied order of a service chain in a network may notnecessarily be a linear progression as the architecture allows for SCsthat copy to more than one branch resulting in a tree- or web-likestructure. Also, an example provider network may support servicearrangements where there is flexibility in the order in which servicefunctions need to be applied. Whereas the term “service chain” is oftenused as a shorthand notation for “service function chain”, in certainstandards and specifications concerning virtualized architectures (e.g.,European Telecommunications Standards Institute (ETSI) NFV standards),SCs are also referred to as VNF Forwarding Graphs. It should thereforebe noted that an SC or VNF Forwarding Graph is essentially a logicaloverlay on the underlying network infrastructure path and a linkinvolving one or more VNFs may overlay a number of underlying physicalnetwork links. Accordingly, the teachings herein are equally applicableto service architectures according to a number of existing standards andspecifications (e.g., ETSI, IETF (Internet Engineering Task Force), ONF(Open Networking Foundation), etc.). Additionally, in certainembodiments of the present application, changing the design of an SCdoes not in general necessarily mean changing the underlyinginfrastructure network topology or forwarding behavior. For example,moving a VNF to a different physical host may only affect the overlayservice flow path rather than altering the underlying IP network routes.

FIG. 4 depicts an analytics-driven network architecture 400 fordynamically configuring or reconfiguring service chaining in anNFV-based service network of FIG. 2 according to an embodiment.Advantageously, a network node or subsystem 402 comprising a dynamicprofile analyzer (DPA) 404 and a dynamic service chain designer (DSCD)406 that is operatively coupled to a service chain management controlsubsystem 410 is provided for receiving dynamic profiles from a dataanalytics platform 408. As set forth in reference to FIG. 1 above, thedata analytics platform 408 may preferably be implemented using Big DataAnalytics architecture that may be cloud-based, enterprisenetwork-based, or even be provided as part of a service network. AnNFV-based domain 412 is illustrative of a virtualized service networkwherein an SC/VNF layer 414 comprising one or more SF/VNFs isimplemented by a virtualization layer 416 that abstracts the underlyingphysical infrastructure resources 418 of the network. An NFV domaininventory database subsystem 420 is operatively coupled to the servicechain management control entity 410 and DSCD 406 of the profileanalysis/designer node 402 for facilitating data storage with respect toSC management, provisioning, policy management as well as dynamic(re)configuration of the network.

For contextualizing the teachings of an embodiment of ananalytics-driven (re)configuration scheme of the present disclosure, oneor more multidimensional state spaces spanning at least a portion of thevarious environmental states relevant to the network, e.g., networkstates, service user behavior states, data flow states,geographic/location-specific conditions, etc., as pointed outhereinabove in respect of FIG. 1, may be constructed wherein a uniqueset of state variables in a multidimensional space may be termed a“situation”. Formally, a situation S_(i), is defined as a set orcombination of events [e_(i)], i.e., S_(i)={e₁, e₂, . . . , e_(N)},wherein the events e_(i) represent network and user states or otherstate variables exhibiting changes (e.g., threshold crossings). Thus, aparticular situation may be considered as an aggregate state of aplurality of events that have relevance to the design of at least aportion of the VNF domain. Corresponding to a particular situation, a“situation profile” may be defined as an N-dimensional vector whereevents (or representative state variables) may take on specific values.Accordingly, a situation profile V_(i) corresponding to S_(i) is avector:

V_(i)=[Ve₁,Ve₂, . . . ,Ve_(N)],

where Ve_(i), for j=1 . . . N, are parameters of events e_(j) and maytake Real or Boolean values, and where each value that one of theparameters Ve_(j) can take corresponds to and quantifies an event [e]that describes a cumulative subscriber and/or network behavior. Itshould be understood that events may be represented as variablescomprising at least one of continuous variables, discrete variables,categorical variables, ordinal variables, real variables, Booleanvariables, probabilistic variables and deterministic variables, or acombination thereof. The actual values that quantify or otherwisemeasure the events of a situation profile may therefore take on suitablevalues correspondingly. As an example, consider a simple situation S_(J)that represents an “Emergency situation at traffic junction J”. Forillustrative purposes, S_(J) is modeled by two events, e₁ and e₂, i.e.,

S_(J)={e₁,e₂},

where Event e₁={the number (x) of mobile subscribers currently beingserved at the base station that covers the location J}, where x may beany integer within a range (e.g., [0, 1000]), and Event e₂={M is true ifthe number (y) of emergency calls currently originating from the basestation serving junction J is greater than a select threshold, else M isfalse}, the variable M being Boolean. The corresponding SituationProfile V_(J) of S_(J) is then given as:

V_(J)=[x,M]

In accordance with the teachings of the present invention, the profileanalysis and dynamic network designer system 402 is provisioned with orotherwise maintains a set of distinctive situations that may be referredto as “characteristic situations” that are described by correspondingcharacteristic situation profiles (CSP), denoted by V_(i) ^(c), i=1 toN, where N is the situation profile (i.e., S-Profile) dimension. Atsystem initialization, an initial empirical set of CSPs may beconfigured by the operator, for example, via a human domain expert, atrainable knowledge-based expert system, etc. Thereafter, the number ofcurrent CSPs in the system may be dynamic and new learned CSPs may beappended to a previous CSP set, which may be used an input to determinedynamic design rules for SC/VNF (re)configuration as will be describedbelow in further detail.

Broadly, the profile analysis and dynamic network designer mechanism ofnetwork node 402 may be described by taking reference to FIG. 5, whichillustrates additional components of the network node 402 in oneparticular embodiment. Reference numeral 500 refers to a block diagramof a profile analysis and dynamic network designer node that illustratesvarious interactions among its constituent components and sub-componentsin one implementation of the network node 402 shown in FIG. 4. Althoughthe components and sub-components of the embodiment 500 areillustratively shown as part of a single entity, it should beappreciated that the structural components and functionalities may bedistributed at different locations in a network architecture. As setforth above in respect of FIG. 4, the data analytics platform 408analyzes historical and dynamic aggregate subscriber population andnetwork behavior data to dynamically generate parameterized profiles 504that continuously feed to a profile matching engine 502 of DPA 404. Inone embodiment, the profile matching engine 502 executing at DPA 404 isoperative to apply suitable multivariate mathematical and statisticalanalytical techniques to find a degree of similarity or matching (e.g.,vector distance) between the received dynamic profiles and existingCSPs, comprising V^(c)={[P_(n)], [P_(s)]}, wherein [P_(n)] represents aplurality of network state events and [P_(s)] represents a plurality ofaggregate subscriber population events. A CSP database 506 may beprovided as part of DPA 404 for storing the initial as well as learnedCSPs. The profile matching engine 502 is further configured to feed thedynamic profiles 508 that match to the corresponding CSPs (within adegree of tolerance, for example) to an automated or automatic designengine 512 operating at or as part of DSCD 406, which uses them as inputconditions for effectuating appropriate design actions 518 based uponsuitable design logic, network resource availability, service policiesand requirements, etc. By way of illustration, such design actionsinclude “Tune VNF/SC”, “Modify VNF/SC”, “Scale VNF/SC up”, “Scale VNF/SCdown”, “Clone VNF/SC”, “Scale VNF/SC Out”, Scale VNF/SC In”, etc. as afew examples. Moreover, DPA 404 and/or its profile matching engine 502is also adapted to store other, non-matching profiles in a historicalprofile database 510 for online and/or offline processing. Preferably, aprofile learning engine 514 operating at or as part of DPA 404 may beconfigured to execute suitable machine learning techniques such as SVMsor SVNs, pattern recognition, AI techniques, adaptive neural networks,clustering and classification techniques, and the like, for adaptivelypredicting/learning and discovering certain profiles that may qualify tobe included in the conditions of the dynamic SC design logic. Suchprofiles may be termed “candidate actionable profiles” (CAPs) 515, whichmay be provided to or posted on a design logic editor 516 operating ator as part of DSCD 406. In one embodiment, the design logic editor 516may be provided as a tool with suitable human machine interface 520(e.g., display, command line interface, etc.) that may be used by adomain expert to define or configure new CSPs based on new, additionaland/or alternative design logic 524 that may be provided by the expert.Although a human domain expert may be employed for providing designlogic inputs in one arrangement, a suitable knowledge-based expertsystem that is user-trainable can also be included in another variationwherein online and/or offline processing may be performed underappropriate supervisory evaluation. DSCD 406 and/or its design logiceditor 516 is operative to post the new CSPs 522 to the CSP database 506of DPA 404 where they can be used by the profile matching engine 502 insubsequent matching operations.

FIG. 6 depicts a flowchart of various blocks, steps, acts and functionsthat may take place in a network (re)configuration scheme 600 accordingto an embodiment. At block 604, at least one dynamic situation profile(DSP) with respect to a particular situation is received from a dataanalytics platform, wherein the dynamic situation profile may be definedin terms of one or more service user behavior events and one or moreevents pertaining to a state of a network servicing a plurality ofservice users. Further, as described above, the dynamic situationprofile provided by the data analytics platform comprises actual valuescorresponding to the service user behavior events and the network stateevents defining the particular situation. A similarity index may bedetermined between the dynamic situation profile and a characteristicsituation profile (CSP) corresponding to the particular situation,wherein the characteristic situation profile comprises allowable values(e.g., threshold values) with respect to the service user behaviorevents and the network state events defining the particular situation(block 606). If the similarity index is within an acceptable window, oneor more control signals may be generated to effectuate a dynamic designchange action for changing configuration of at least a part of thenetwork operating to service user data flows of the service users (block608). In one variation, the data analytics platform may be trained viaadaptive learning to facilitate generating appropriately parameterizeddata relative to the situations defined for network (block 603).Similarly, an initial CSP set may be provisioned or otherwise configuredin order to facilitate profile matching evaluations in the beginningstages of the process (block 605).

In an optional arrangement, a profile learning and CSP updating process610 may be included that may be performed either online, offline,real-time, or in some batch mode, in a configurable manner. A historicalprofile database may include not only the dynamic profiles that did notmatch corresponding CSPs but also indications of the matching profilesthat may be provided to a trainable profile learning scheme.

As pointed out previously, a similarity index between the dynamicsituation profile and the characteristic situation profile may beobtained as a multidimensional vector or metric distance using a varietyof techniques. For example, such “distances” may comprise at least oneof Euclidean distances, Hamming distances, Chebychev distances,Minkowsky distance, Mahalanobis distances and Bhattacharyya distances,etc. Further, various “inner product” type techniques (e.g., covariance)may also be used in estimating or otherwise measuring a degree ofsimilarity or dissimilarity (which can be a deterministic estimate or aprobabilistic estimate) between the two profiles' events data.Furthermore, the dimensionality of a received dynamic situation profileand the corresponding characteristic situation profile need notnecessarily be the same for purposes of measuring similarity ordistance.

Example applications of the foregoing teachings may be illustrated bytaking reference to a few simple use case scenarios. In the example of asituation S_(J) describing the number of mobile users and the number ofemergency calls at a traffic junction J as set forth hereinabove, thecorresponding CSP may be defined as:

V^(c) _(J)=[x=500,M=1]

That is to say, a CSP corresponding to an “emergency situation atjunction J” is defined as (≧) 500 subscribers being connected to theserving base station and at least two emergency calls taking place. Herethe Boolean variable M=1, meaning logic True or high, although aninverse logic value may also be used in another embodiment. It shouldalso be noted that parameters can take real values; therefore aprobabilistic characterization of events and situations is alsopossible. Accordingly, in one embodiment, when a dynamic situationprofile (DSP) corresponding to S_(J) is received by the profile matchingengine, it may be analyzed to check if it matches or crosses thethreshold values established in the above CSP, whereupon a suitabledynamic design change action may be effectuated.

In another more evolved yet simple example that uses additionalcapabilities of a data analytics platform, a CSP may involve morecomplex and dynamic parameters or variables. For example, for the sameSituation S_(J) above, consider the following events e₃ and e₄:

-   -   e₃={there are currently x mobile subscribers more than average        at a particular time of day at the base station serving junction        J}    -   e₄={M is true if there are more emergency calls (by a specified        number, e.g., y=2) than the average number of emergency calls        originating across base stations with close utilization        statistics, e.g., average and variance, to the base station        serving junction J, else M is false}.

A corresponding example Characteristic Profile V^(c2) _(J) of S_(J) maybe set as below:

V^(c2) _(J)=[x=20,M=1]

When a received DSP is compared against this CSP and if there is a matchand/or the established thresholds are crossed, a suitable design changeaction may be generated by the system accordingly.

In a still further use case scenario with a more elaborate setting, thefollowing conditionalities may be considered: (i) the data analyticsplatform is operative to characterize the subscriber population based ononline behavior patterns and classify them into “early adopters”,“majority” and “laggards” with respect to adopting a particular newtechnological device; (ii) the data analytics platform is also operativeto characterize the subscriber population according to their recent(e.g., last month) electronic device (smartphone, printer, tablet, etc.)interests; (iii) the NFV domain operator offers a service to advertiserswhere the streamed advertisement content adapts to the current onlinesubscriber home and mobile viewers' population profiles and preferencesand the streamed contents shown (e.g., sports, sci-fi films, musicalshows, etc.); and (iv) to avoid over-engineering cloud resourceallocation (e.g., compute resources, storage resources, networkresources, or any combination thereof) to any particular kind ofadvertisement content, the required resources are VNF-based and arecreated, consumed, and extinguished according to optimal advertisingeffect rules. Consider the Situation S_(k) named “Advertise new SmartTVduring NBA game” that is defined as below:

S_(k)={e₁,e₂,e₃,e₄},

where

-   -   e₁={less than x days to Black Friday}    -   e₂={more than y viewers watching NBA playoffs in City X tonight}    -   e₃={the ratio of early adopters in City X is currently z %}    -   e₄={the average online search intensity for TVs is N out of 10        in the last M days}

A Situation Profile (S-Profile) for S_(k) may then be set as below:

V_(k)=[x,y,z,N,M]

wherein a corresponding CSP profile may be defined as the following:

V^(c) _(k)=[10,100000,20%,7,10]

A dynamic design action may be established to create new resources forbroadcasting a smartTV advertisement just for the viewers of the NBAgame of City X within the next 10 minutes. Example dynamicallyconfigurable VNF resources may include replicating content to newtemporary VNF storage server, via a temporary VNF streamer, and settingup overlay path(s) between VNF servers and a point of presence (POP)node for City X.

To further demonstrate how such a design action could be recommended bythe system as a candidate S-Profile, consider the additional event:e5={true if early adopters from City X bought new TVs around the time ofNBA playoffs}. Then raw values of the profile containing the extraparameter, i.e., [x, y, z, N, M, q], can be provided to a clusteringalgorithm that can determine the nearest vector cluster center whereq=True. Such a clustering analysis can provide appropriate eventparameter values that may then be used to formulate a V^(c) _(k) as thecorresponding CSP.

In view of the foregoing, an embodiment of a profile analysis anddynamic network designer subsystem (e.g., as depicted in FIGS. 4 and 5)may involve two main process flows: (i) a real-time dynamic chain designprocess flow that is concerned with generating appropriate design changeactions based on incoming DSPs, and (ii) an offline CSP update flow foradaptively learning new CSPs based on historical profiles. It should beappreciated that these process flows may be also executed in a singleflow, e.g., two parallel flows on a real-time basis. To recapitulate, areal-time dynamic design chain flow involves the following:

-   -   (A) The data analytics platform continuously feeds the DPA        element with dynamic situation profiles, which may be        represented as event vectors corresponding to the environmental        states of design interest.    -   (B) In DPA, the profile matching engine uses techniques such as        vector analysis to estimate an appropriately defined distance of        the incoming raw profile vectors to corresponding CSPs. If the        matching distance or similarity index lies within some        predefined tolerance, the matching profiles and/or the        indications of the matching result may be forwarded to DSCD        component. As pointed out previously, examples of vector        distance include Euclidean, Hamming, Mahalanobis or other vector        distance definition, depending on the vector analysis technique        used.    -   (C) In DSCD, an auto-design engine contains design rules whose        conditions are evaluated based on the occurrence of individual        CSPs or combinations thereof, which effectuate suitable design        change actions relative to the network.

As to the CSP update/learning flow, an embodiment may involve thefollowing:

-   -   (A) In DPA, non-matching profiles may be stored in a historical        profile database, e.g., for offline post-processing. The profile        learning engine uses machine learning methods such as, e.g.,        clustering (k-means, support vector machines, hierarchical        clustering, etc.) and classification (Bayesian, feature vectors,        etc.) techniques, as described hereinabove. The output of this        analysis comprises candidate actionable profiles (CAPs), i.e.,        profile vectors that can adequately represent clusters of        frequently occurring similar (or close) profile vectors and, as        such, show the potential to represent CSPs. Such CAPs may be        forwarded to the DSCD component.    -   (B) In DSCD, the CAPs may be posted on the design logic editor        that may be used by a human domain expert. Preferably, the        design logic editor can be used to incorporate the posted CAPs        into the set of CSPs and plug in conditional expressions of        existing or new automatic design rules and map them to        appropriate design actions. Further, the design logic editor may        also be used by the human expert to define new rules based on        CSPs and map them to corresponding actions from scratch.

In broad terms, design change actions may be classified, but notlimited, into the following general groups: (i) dynamic VNF topologydesign (e.g., placement of SF/VNFs or assignment of service nodes in achain, (re)instantiation of additional VNFs, etc.); (ii) dynamic servicechain network/topology design (e.g., (re)arranging the order or sequenceof VNFs in a service chain); (iii) dynamic VNF management andorchestration, which also enables dynamic capacity planning and dynamicresource management (e.g., VM capacity management); and (iv) dynamicservice chain management and orchestration (e.g., adding or terminatingvarious end-to-end service chains within the network). In addition tothe example design change actions set forth elsewhere in the presentpatent application, the following example actions may also beimplemented in additional exemplary embodiments: (i) Tune ServiceChaining—e.g., add a new DPI field based on the analytics-driven newdynamic profiles; (ii) Alter Service Chain VNF Members—e.g., add a newSecurity Service Function in Service Chain to prevent DistributedDenial-of-Service (DDOS) attacks based on information retrieved fromanalytics driven new dynamic profiles or set up Service Chain withminimal service functions to cater to Emergency traffic; (iii) Scaling(Autoscaling or triggered) Service Functions within Service Chains—e.g.,add a new virtual DPI server to accommodate the traffic (e.g., based onnumber of connections) in a particular geographical location; (iv) CloneService Chains—e.g., for distributing resource demand over differentgeographical locations; and (v) Re-route Service Chains—e.g., performload balancing.

FIG. 7 depicts a flowchart of various blocks, steps, acts and functionsthat may take place according to another embodiment wherein both onlineand offline process flows are integrated into a network(re)configuration and CSP learning scheme 700. At block 702, dynamicsituation profiles {[P_(n)], [P_(s)]} are received, wherein [P_(n)]represents a plurality of network state events and [P_(s)] represents aplurality of aggregate subscriber population events. A similaritymeasurement, value, index, indicium, or metric is checked between theDSPs and existing CSPs (block 704). Upon determining that there is amatching (within a guard band, for example), design rules in anAuto-Design engine are evaluated in view of the matched profiles (blocks706, 708). Appropriate dynamic service chain (DSC) action such as, e.g.,regulate a VNF, copy VNF(s), cloning of a chain, etc. may then beeffectuated (block 710). Where the received DSPs do not matchcorresponding CSPs, they are appended to or stored in a profile historydatabase (block 712), from which candidate profiles may be generated,derived, determined or otherwise obtained (block 714). As discussedabove, the candidate profiles may be developed into new CSPs undersupervisory evaluation, which new CSPs may be added to the CSP databasefor subsequent matching analyses. The new candidate profiles may also beposted to a user tool-kit for further evaluation (block 716).

FIG. 8 depicts a block diagram of an apparatus 800 that may beconfigured to interoperate in an analytics-driven network architectureaccording to an embodiment of the present patent disclosure. It shouldbe appreciated that apparatus 800 may be implemented as a network nodeor element for realizing at least a portion of a profile analysis anddynamic network designer subsystem set forth above in respect of theembodiments shown in FIG. 1, 4 or 5. Depending on the implementation,apparatus 800 may be configured as DPA component, DSCD component, or acombination of both. Accordingly, a profile matching engine 804, aprofile learning engine 810, a design change engine 814 as well as adesign logic editor 816 may be provided in any suitable combination forinteroperating according to one or more embodiments set forth hereinunder the control of one or more processors 802 and applicable programcode or instructions 808 provided in a persistent memory. A CSP database806 as well as a historical profile database 806 may also be included inan embodiment of apparatus 800, although such databases may be providedelsewhere in a network. Interfaces 820-1 to 820-M are representative ofnetwork interfaces that a DPA arrangement of apparatus 800 may utilizein accessing one or more components of a distributed data analyticsplatform for receiving dynamic situation profile data as well ascoupling to a DSCD arrangement (that is not part of apparatus 800). Insimilar fashion, interfaces 818-1 to 818-K represent network interfacesthat a DSCD arrangement of apparatus 800 may utilize for coupling to aDPA arrangement (that is not part of apparatus 800) as well asappropriate service chain management and control element(s) of aconfigurable network. A user interface 812 may be provided forfacilitating interactions by a human domain expert as part of the designlogic editor 816. Although not explicitly shown in this FIG., oneskilled in the art will recognize that appropriate memory storage may bealso provided for storing design rules, policies, service chainrequirements, etc. with respect to subscriber data flows in the network.Accordingly, depending on the context, interfaces selected from theforegoing interfaces may sometimes be referred to as a first interface,a second interface, and the like in a particular embodiment. Moreover,the hardware resources and DPA/DSCD functionalities of the apparatus 800may themselves be at least partially virtualized in alternative oradditional arrangements.

Based upon the foregoing Detailed Description, it should be appreciatedthat embodiments of the present disclosure provide a method and systemthat leverages Big Data Analytics to dynamically derive suitable rulesfor the creation and design of service chains including configuration,ordering, dimensioning and assignment of their component VNFs. Such(re)design actions are advantageously provided as operations that may beperformed by considering the end-to-end service as a whole in responseto dynamic, possibly composite events provided by the analyticsplatform. Service chain (re)design according to the teachings herein maytypically change one or more VNFs and, as a result, the SC functionalcharacteristics as a whole (e.g., capacity, quality etc.). Moreover, itmay impact the treatment of all existing or arriving flow aggregatesrelated to the SC in a provider network. It should be appreciated thatthe (re)design paradigm captured in the embodiments herein is contraryto the mere action of steering an individual subscriber's traffic flowthrough a static SC based on the subscriber's service requirements.Instead, the dynamic SC (re)design methodology of the present disclosureadapts the SCs and associated traffic in a network according to thereal-time conditions monitored and curated by the Big Data Analytics.Furthermore, the teachings set forth herein are also applicable tomulti-cloud and hybrid virtual/physical node networks.

Additional advantages of the embodiments of the present patentdisclosure may be cataloged as follows: (i) Requirement Diversity: Usingaggregate subscriber population profiling to guide NFV and SC design and(re)configuration as opposed to techniques that merely use individualsubscriber flow requirements. Subscriber population profiles can be usedin the embodiments to capture a richer set of requirements than justtraffic flow performance. For example, subscriber geography trends,application trends, or subscriber and service trends can project servicedemands and make more informed design decisions. (ii) Faster DesignConvergence: Profile aggregation supports SC design using cumulativetrends rather than incremental optimization based on incoming flows.(iii) Design Adaptability: Dynamic SC design based on real-time and/orup-to-date historical subscriber behavior profiling corresponds betterto current subscriber requirements rather than those previouslyregistered. (iv) Design Proactivity: Capability to leverage predictiveanalytics so as to act proactively on expected events. (v) DesignDiversity: Capability to combine subscriber and network events in designdecisions.

In the above-description of various embodiments of the presentdisclosure, it is to be understood that the terminology used herein isfor the purpose of describing particular embodiments only and is notintended to be limiting of the invention. Unless otherwise defined, allterms (including technical and scientific terms) used herein have thesame meaning as commonly understood by one of ordinary skill in the artto which this invention belongs. It will be further understood thatterms, such as those defined in commonly used dictionaries, should beinterpreted as having a meaning that is consistent with their meaning inthe context of this specification and the relevant art and may not beinterpreted in an idealized or overly formal sense expressly so definedherein.

At least some example embodiments are described herein with reference toblock diagrams and/or flowchart illustrations of computer-implementedmethods, apparatus (systems and/or devices) and/or computer programproducts. It is understood that a block of the block diagrams and/orflowchart illustrations, and combinations of blocks in the blockdiagrams and/or flowchart illustrations, can be implemented by computerprogram instructions that are performed by one or more computercircuits. Such computer program instructions may be provided to aprocessor circuit of a general purpose computer circuit, special purposecomputer circuit, and/or other programmable data processing circuit toproduce a machine, so that the instructions, which execute via theprocessor of the computer and/or other programmable data processingapparatus, transform and control transistors, values stored in memorylocations, and other hardware components within such circuitry toimplement the functions/acts specified in the block diagrams and/orflowchart block or blocks, and thereby create means (functionality)and/or structure for implementing the functions/acts specified in theblock diagrams and/or flowchart block(s). Additionally, the computerprogram instructions may also be stored in a tangible computer-readablemedium that can direct a computer or other programmable data processingapparatus to function in a particular manner, such that the instructionsstored in the computer-readable medium produce an article of manufactureincluding instructions which implement the functions/acts specified inthe block diagrams and/or flowchart block or blocks.

As alluded to previously, tangible, non-transitory computer-readablemedium may include an electronic, magnetic, optical, electromagnetic, orsemiconductor data storage system, apparatus, or device. More specificexamples of the computer-readable medium would include the following: aportable computer diskette, a random access memory (RAM) circuit, aread-only memory (ROM) circuit, an erasable programmable read-onlymemory (EPROM or Flash memory) circuit, a portable compact discread-only memory (CD-ROM), and a portable digital video disc read-onlymemory (DVD/Blu-ray). The computer program instructions may also beloaded onto or otherwise downloaded to a computer and/or otherprogrammable data processing apparatus to cause a series of operationalsteps to be performed on the computer and/or other programmableapparatus to produce a computer-implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions/acts specified inthe block diagrams and/or flowchart block or blocks. Accordingly,embodiments of the present invention may be embodied in hardware and/orin software (including firmware, resident software, micro-code, etc.)that runs on a processor such as a digital signal processor, which maycollectively be referred to as “circuitry,” “a module” or variantsthereof.

Further, in at least some additional or alternative implementations, thefunctions/acts described in the blocks may occur out of the order shownin the flowcharts. For example, two blocks shown in succession may infact be executed substantially concurrently or the blocks may sometimesbe executed in the reverse order, depending upon the functionality/actsinvolved. Moreover, the functionality of a given block of the flowchartsand/or block diagrams may be separated into multiple blocks and/or thefunctionality of two or more blocks of the flowcharts and/or blockdiagrams may be at least partially integrated. Finally, other blocks maybe added/inserted between the blocks that are illustrated and blocksfrom different flowcharts may be combined, rearranged, and/orreconfigured into additional flowcharts in any combination orsubcombination. Moreover, although some of the diagrams include arrowson communication paths to show a primary direction of communication, itis to be understood that communication may occur in the oppositedirection relative to the depicted arrows.

Although various embodiments have been shown and described in detail,the claims are not limited to any particular embodiment or example. Noneof the above Detailed Description should be read as implying that anyparticular component, module, element, step, act, or function isessential such that it must be included in the scope of the claims.Reference to an element in the singular is not intended to mean “one andonly one” unless explicitly so stated, but rather “one or more” or “atleast one”. All structural and functional equivalents to the elements ofthe above-described embodiments that are known to those of ordinaryskill in the art are expressly incorporated herein by reference and areintended to be encompassed by the present claims. Accordingly, thoseskilled in the art will recognize that the exemplary embodimentsdescribed herein can be practiced with various modifications andalterations within the spirit and scope of the claims appended below.

What is claimed is:
 1. A network configuration method, comprising:receiving, from a data analytics platform, a dynamic situation profilewith respect to a particular situation defined in terms of one or moreservice user behavior events and one or more events pertaining to astate of a network servicing a plurality of service users, wherein thedynamic situation profile comprises values corresponding to the serviceuser behavior events and the network state events defining theparticular situation; determining a similarity index between the dynamicsituation profile and a characteristic situation profile correspondingto the particular situation, wherein the characteristic situationprofile comprises allowable values with respect to the service userbehavior events and the network state events defining the particularsituation; and if the similarity index is within an acceptable window,generating one or more control signals to effectuate a dynamic designchange action for changing configuration of at least a part of thenetwork operating to service user data flows of the service users. 2.The method as recited in claim 1, wherein the network comprises aservice network having a plurality of virtualized service functions andfurther wherein the design change action comprises at least one ofinstantiating a new virtualized service function, rearranging one ormore existing virtualized service functions, generating one or moreinstances of an existing virtualized service function, cloning anexisting service chain of one or more virtualized service functions,rerouting an existing service chain of one or more virtualized servicefunctions, instantiating additional virtual machine resources, andremoving one or more virtualized service functions.
 3. The method asrecited in claim 1, wherein one or more of the service user behaviorevents and the network state events are represented as variablescomprising at least one of continuous variables, discrete variables,categorical variables, ordinal variables, real variables, Booleanvariables, probabilistic variables and deterministic variables.
 4. Themethod as recited in claim 1, wherein the dynamic situation profile andthe characteristic situation profile each comprise a vector.
 5. Themethod as recited in claim 1, further comprising: if the similarityindex is not within the acceptable window, appending the dynamicsituation profile to a historical profile database and executing aprofile learning engine operative to analyze the appended dynamicsituation profile in view of a history of profiles with respect to theparticular situation; and receiving a supervisory evaluation, at adesign logic editor, with respect to the history of profiles of theparticular situation and deriving a candidate characteristic situationprofile that is operative as a new characteristic situation profile forthe particular situation.
 6. The method as recited in claim 5, whereinthe supervisory evaluation is received from at least one of aknowledge-based expert system and a human domain expert.
 7. The methodas recited in claim 2, wherein the service network is configured as aSoftware-Defined Network (SDN) based on one of OpenFlow protocol andForwarding and Control Element Separation (ForCES) protocol.
 8. Themethod as recited in claim 1, wherein the similarity index between thedynamic situation profile and the characteristic situation profile isobtained as a vector distance comprising at least one of a Euclideandistance, a Hamming distance, a Chebychev distance, a Minkowskydistance, a Mahalanobis distance and a Bhattacharyya distance.
 9. Themethod as recited in claim 1, wherein the similarity index between thedynamic situation profile and the characteristic situation profile isobtained based on a probabilistic dissimilarity between the twoprofiles' events data.
 10. The method as recited in claim 1, furthercomprising: initializing a set of characteristic situation profilescorresponding to a number of predefined situations; and updating the setof characteristic situation profiles based on supervisory evaluation ofdynamic situation profiles received from the data analytics platform.11. A network element, comprising: a profile analyzer operative toreceive from a data analytics platform a dynamic situation profile withrespect to a particular situation defined in terms of one or moreservice user behavior events and one or more events pertaining to astate of a network servicing a plurality of service users, wherein thedynamic situation profile comprises values corresponding to the serviceuser behavior events and the network state events defining theparticular situation; a matching module associated with the profileanalyzer for determining a similarity index between the dynamicsituation profile and a characteristic situation profile correspondingto the particular situation, wherein the characteristic situationprofile comprises allowable values with respect to the service userbehavior events and the network state events defining the particularsituation; and a dynamic service chain designer, responsive to receivingan indication that the similarity index between the dynamic situationprofile and the characteristic situation profile is within an acceptablewindow, operative for generating one or more control signals toeffectuate a dynamic design change action for changing configuration ofat least a part of the network operating to service user data flows ofthe service users.
 12. The network element as recited in claim 11,wherein the network comprises a service network having a plurality ofvirtualized service functions and further wherein the design changeaction comprises at least one of instantiating a new virtualized servicefunction, rearranging one or more existing virtualized servicefunctions, generating one or more instances of an existing virtualizedservice function, cloning an existing service chain of one or morevirtualized service functions, rerouting an existing service chain ofone or more virtualized service functions, instantiating additionalvirtual machine resources, and removing one or more virtualized servicefunctions.
 13. The network element as recited in claim 12, wherein oneor more of the service user behavior events and the network state eventsare represented as variables comprising at least one of continuousvariables, discrete variables, categorical variables, ordinal variables,real variables, Boolean variables, probabilistic variables anddeterministic variables.
 14. The network element as recited in claim 12,wherein the dynamic situation profile and the characteristic situationprofile each comprise a vector.
 15. The network element as recited inclaim 12, further comprising: a historical profile database that ispopulated with dynamic situation profiles that do not matchcorresponding characteristic situation profiles within respectivedegrees of tolerance; a profile learning engine operative to generatecandidate actionable profiles based on analyzing the historicalprofiles; and a design logic editor configured to receive supervisoryevaluations with respect to the candidate actionable profiles forproviding new characteristic situation profiles.
 16. The network elementas recited in claim 15, wherein the design logic editor is configured toreceive a supervisory evaluation from at least one of a knowledge-basedexpert system and a human domain expert.
 17. The network element asrecited in claim 12, wherein the service network is configured as aSoftware-Defined Network (SDN) based on one of OpenFlow protocol andForwarding and Control Element Separation (ForCES) protocol.
 18. Thenetwork element as recited in claim 11, wherein the matching module isconfigured to generate a similarity index between the dynamic situationprofile and the characteristic situation profile that is obtained as avector distance comprising at least one of a Euclidean distance, aHamming distance, a Chebychev distance, a Minkowsky distance, aMahalanobis distance and a Bhattacharyya distance.
 19. The networkelement as recited in claim 11, wherein the matching module isconfigured to generate a similarity index between the dynamic situationprofile and the characteristic situation profile that is obtained basedon a probabilistic dissimilarity between the two profiles' events data.20. The network element as recited in claim 11, further comprising: adatabase including a set of initial characteristic situation profilescorresponding to a number of predefined situations, wherein the set ofcharacteristic situation profiles is updated based on supervisoryevaluation of dynamic situation profiles received from the dataanalytics platform.
 21. The network element as recited in claim 11,wherein at least one of the profile analyzer, the matching module andthe dynamic service chain designer is implemented as a virtual networkfunction.
 22. The network element as recited in claim 11, wherein theprofile analyzer, the matching module and the dynamic service chaindesigner are configured to interoperate with an orchestrator nodeassociated with the network.
 23. The network element as recited in claim11, wherein the profile analyzer, the matching module and the dynamicservice chain designer are configured to operate as an orchestrator nodeassociated with the network.
 24. A non-transitory computer-readablemedium containing instructions stored thereon which, when executed by acomputer system configured to operate as an apparatus in a servicenetwork, perform the acts: upon receiving, from a data analyticsplatform, dynamic situation profiles with respect to one or more serviceuser behavior events and one or more events pertaining to a state of anetwork servicing a plurality of service users, determining if thedynamic situation profiles match corresponding characteristic situationprofiles, wherein the characteristic situation profiles comprisesthreshold values with respect to the service user behavior events andthe network state events; forwarding one or more dynamic situationprofiles that match the corresponding characteristic situation profileto a design action module for generating appropriate control signals forchanging configuration of at least a part of the network operating toservice user data flows of the service users; storing one or moredynamic situation profiles that do not match the correspondingcharacteristic profiles in a historical profile database; and causing toexecute a profile learning module for determining a set of candidateactionable profiles for inclusion into a current characteristicsituation profile database under supervisory evaluation.